Closed Bug 1550462 Opened 6 years ago Closed 17 days ago

Implement pointerrawupdate event

Categories

(Core :: DOM: Events, enhancement, P3)

Product:
Core
Component:
DOM: Events
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
140 Branch
Tracking Flags:
Tracking Status
relnote-firefox --- ?
firefox140 --- fixed

People

(Reporter: hsinyi, Assigned: masayuki)

References

(Depends on 2 open bugs, Blocks 4 open bugs,
URL
)

Details

(Keywords: dev-doc-complete, parity-chrome)

User Story

platform-scheduled:2025-06-30

Attachments

(3 files)

Bug 1550462 - part 1: Define pointerawupdate event r=smaug
48 bytes, text/x-phabricator-request
Details | Review
Bug 1550462 - part 2: Make PresShell::HandleEvent dispatch preceding pointerrawupdate event r=smaug,edgar,#dom-core
48 bytes, text/x-phabricator-request
Details | Review
Bug 1550462 - part 3: Enable `pointerrawupdate` event r=smaug!
48 bytes, text/x-phabricator-request
Details | Review
Blocks: 822898
Priority: -- → P3
Severity: normal → S3
Blocks: pointerevent
No longer blocks: 822898
Blocks: 1655753
Assignee: nobody → masayuki
Status: NEW → ASSIGNED
OS: Unspecified → All
Hardware: Unspecified → All
See Also: → https://github.com/w3c/pointerevents/issues/509
User Story: (updated)

Also requested on Connect: https://connect.mozilla.org/t5/ideas/support-for-pointerrawupdate/idi-p/89299

This patch just defines the event message, an atom for event listener attribute
and managing whether the window may have a listener.

Depends on D243402

Attachment #9475249 - Attachment description: Bug 1550462 - part 2: Make `PresShell::HandleEvent` dispatch preceding `pointerrawupdate` event r=smaug! → Bug 1550462 - part 2: Make `PresShell::HandleEvent` dispatch preceding `pointerrawupdate` event r=smaug!,#dom-core

Please take care to avoid the following Chrome bugs with pointerrawupdate which so far have remained unfixed:

https://issues.chromium.org/issues/353249342
https://issues.chromium.org/issues/40817651
https://issues.chromium.org/issues/40683756

Would it be possible to get a test for https://github.com/w3c/pointerevents/issues/509 in some bug? Maybe a followup

(In reply to Olli Pettay [:smaug][bugs@pettay.fi] from comment #6)

Would it be possible to get a test for https://github.com/w3c/pointerevents/issues/509 in some bug? Maybe a followup

Filed bug 1965118. I'll work on that once I finished working on current Interop work which should be done by end of June.

Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/aae164cff6aa part 1: Define `pointerawupdate` event r=smaug https://hg.mozilla.org/integration/autoland/rev/5718f7f3067e part 2: Make `PresShell::HandleEvent` dispatch preceding `pointerrawupdate` event r=smaug,dom-core,edgar
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/93856bf75c44 part 3: Enable `pointerrawupdate` event r=smaug

https://hg.mozilla.org/mozilla-central/rev/aae164cff6aa
https://hg.mozilla.org/mozilla-central/rev/5718f7f3067e
https://hg.mozilla.org/mozilla-central/rev/93856bf75c44

Status: ASSIGNED → RESOLVED
Closed: 18 days ago
status-firefox140: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
Blocks: 1965118
No longer depends on: 1965118
Pushed by amarc@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f8a2a169b296 Revert "Bug 1550462 - part 3: Enable `pointerrawupdate` event r=smaug" for causing mochitest failures @ test_pointerrawupdate_event_count.html

Backed out for causing mochitest failures @ test_pointerrawupdate_event_count.html

Status: RESOLVED → REOPENED
status-firefox140: fixed → ---
Flags: needinfo?(masayuki)
Resolution: FIXED → ---
Target Milestone: 140 Branch → ---

Hmm, xorig test framework is really unstable for pointer events...

Flags: needinfo?(masayuki)
Attachment #9475248 - Attachment description: Bug 1550462 - part 1: Define `pointerawupdate` event r=smaug!,#dom-core → Bug 1550462 - part 1: Define pointerawupdate event r=smaug
Attachment #9475249 - Attachment description: Bug 1550462 - part 2: Make `PresShell::HandleEvent` dispatch preceding `pointerrawupdate` event r=smaug!,#dom-core → Bug 1550462 - part 2: Make PresShell::HandleEvent dispatch preceding pointerrawupdate event r=smaug,edgar,#dom-core
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/32ba02fa32ec part 1: Define pointerawupdate event r=smaug https://hg.mozilla.org/integration/autoland/rev/37f6acd499b1 part 2: Make PresShell::HandleEvent dispatch preceding pointerrawupdate event r=smaug,dom-core,edgar
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/ccd6d2c97e41 part 3: Enable `pointerrawupdate` event r=smaug

https://hg.mozilla.org/mozilla-central/rev/32ba02fa32ec
https://hg.mozilla.org/mozilla-central/rev/37f6acd499b1
https://hg.mozilla.org/mozilla-central/rev/ccd6d2c97e41

Status: REOPENED → RESOLVED
Closed: 18 days ago → 17 days ago
status-firefox140: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch

:masayuki could you consider nominating this for a release note? (Process info)

Flags: needinfo?(masayuki)

Release Note Request (optional, but appreciated)
[Why is this notable]: Introducing a new API.
[Affects Firefox for Android]: Yes.
[Suggested wording]: pointerrawupdate event is now supported. The event allows the web apps to handle pointermove immediately. However, this event is fired more frequently than pointermove with another hit test for considering the target. Therefore, even only adding an event listener of pointerrawupdate makes the damage to the performance. So, this is intended to improve apps which cannot handle user input smoothly only with coalesced pointermove events.
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/API/Element/pointerrawupdate_event

relnote-firefox: --- → ?
Flags: needinfo?(masayuki)

Thanks, added to the Fx140 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx140 release notes.

QA Whiteboard: [qa-triage-done-c141/b140]

FF140 MDN docs work for this done in https://github.com/mdn/content/issues/39614

Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: